• JProxy is:

• HTTP / HTTPS Tunnel for EJB, RMI, JMS or CORBA
  
• Asynchronous message delivery for JMS thru HTTP / HTTPS even thru firewall
• The Generic Provider-Independent HTTP /HTTPS Tunneling for different EJB, JMS or CORBA servers
• Applet utilizing EJB, RMI, JMS, or CORBA without downloading Java Plug-in
• The way to solve scalability or failover for EJB or CORBA
• The EJB, RMI, JMS or CORBA support for your custom communication protocols.
• The solution to increase performance of communication by utilizing data compression and packaging multiple orthogonal requests

  JProxy is a thin customizable layer for access distributed services and objects from Java. The layer may be applied for such APIs as CORBA, EJB, RMI, JMS, JNDI. It encapsulates provider's specifics of distributed services. It also allows customization of distributed object access in order to achieve better performance, fail-over, scalability. HTTP-Tunneling is one of application of the idea.
  

  Check a live sample applets utilizing EJB, JMS, or CORBA

Get a free binary release of JProxy and try it for your applications

JProxy is a product that solves number of intercommunication problems between Java Client and J2EE and/or CORBA Services.
JProxy provides HTTP / HTTPS Tunneling for well-known APIs: EJB, RMI, JNDI, JMS and CORBA.
JProxy allows encapsulation of specifics of different J2EE and CORBA servers.

JProxy helps to solve scalability or fail-over problems. The API allows satisfying different demands: Data Compression, Security, and Fault-tolerance. JProxy may integrate variety of EJB or CORBA Application Servers from different providers into one system.

JProxy Server generates its own client stubs for remote object. The stubs are completely independent from original stubs of remote object. Any communication protocols or data marshalling may be used in the stubs. The stubs may be customized in order to handle fail-over, load balancing, or optimization of communication.

JProxy may automatically package number of orthogonal requests to the server in one package and perform them as one request, which tremendously reduces traffic on such slow connections as Dial-up connection.

JProxy may seamlessly deliver asynchronous messages from JMS to client thru any firewall. For HTTP client-side callback support JProxy API utilizes two models: Client-side HTTP Server and HTTP Polling. Te polling allows receiving messages as quick as they come. Delay of message delivery is not related with polling period time. For example polling period time may be 1 minute, but JProxy client is still able to receive messages coming every second.
Each JMS message will be performed in separate thread.

A Client's requests are serialized to one communication thread that allows saving client's resources.

JProxy works in standard Java Security Sand-Box! You don't have to change java policy or to use your Security Manager at all! JProxy API provides for Applet or Application transparent access thru any protocol to J2EE or CORBA resources. If you want to use EJB or CORBA from Applet, consider using JProxy.

JProxy with RMI/EJB/JMS/CORBA was also successfully tested on Microsoft's JVM under IE 5.5, which by default does not support the APIs!

More about JProxy...